Overload management for internet of things (iot) gateways

ABSTRACT

Systems and methods for overload management of Internet-of-Things (IoT) gateways. In some embodiments, an Information Handling System (IHS) may include a processor and a memory coupled to the processor, the memory including program instructions stored thereon that, upon execution by the processor, cause the IHS to: detect an overload condition in the IHS; in response to the detection, compare a current volatility of a data field against a volatility baseline for that data field, wherein the data field is one of a plurality of other fields contained within a packet communicated between an IoT device and the IHS; and take responsive action based, at least in part, upon the comparison.

FIELD

The present disclosure generally relates to Information Handling Systems(IHSs), and, more particularly, to systems and methods for overloadmanagement of an Internet-of-Things (IoT) gateway.

BACKGROUND

A new revolution is gaining momentum—a surge of innovation that involvesvast ecosystems of sensors, devices, and networks that can transmit andreceive data. With an estimated number of connected “things” reachingover 25 billion by 2020, the “Internet-of-Things” (IoT) is widelyregarded as the next technological frontier.

Existing IoT deployments range from single device implementations tomassive cross-platform systems that include tens, hundreds, or sometimesthousands of heterogeneous devices. Tying it all together are differentcommunication protocols that enable these various components to talk toeach other.

Because IoT is still in its infancy, however, its underlyingtechnologies remain fractured. Alliances and coalitions are being formedin hopes of someday unifying the IoT landscape. But, at the presenttime, there is still no central IoT standard or deployment oversight.Consumers and providers continue to face ever-increasing deployment,architecture, analytics, and security challenges.

SUMMARY

Embodiments of systems and methods for overload management ofInternet-of-Things (IoT) gateways are described. In an illustrative,non-limiting embodiment, an Information Handling System (IHS) comprisesone or more processors and a memory coupled to the one or moreprocessors, the memory including program instructions stored thereonthat, upon execution by the one or more processors, cause the IHS to:detect an overload condition in the IHS; in response to the detection,compare a current volatility of a data field against a volatilitybaseline for that data field, wherein the data field is one of aplurality of other fields contained within a packet communicated betweenan Internet-of-Things (IoT) device and the IHS; and take responsiveaction based, at least in part, upon the comparison.

In various embodiments, one or more of the following may be implemented:the overload condition may include at least one of: a core temperatureabove a threshold, latency or error rate above another threshold, or aservice outage. The volatility baseline may be created based uponhistorical metrics associated with the data field. The volatilitybaseline may be built by populating a volatility model with dataobtained from inspecting previous packets communicated between the IoTdevice and the IHS. The volatility model may include a list of datafields to be obtained from each packet communicated to the IHS. Theresponsive action may include at least one of: postponing an operation,reducing the size of the data field, re-routing the communication to adifferent interface, passing the IoT device to another IHS, or disablingthe IoT device. The responsive action may include reducing a packetcollection rate for subsequent packets communicated between the IoTdevice and the IHS. The responsive action may include instructing theIoT device to reduce a data acquisition rate of a sensor within the IoTdevice.

In another illustrative, non-limiting embodiment, a method may implementone or more of the aforementioned operations. In yet anotherillustrative, non-limiting embodiment, a hardware memory device may haveprogram instructions stored thereon that, upon execution by an IHS,cause the IHS to perform one or more of the aforementioned operations.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention(s) is/are illustrated by way of example and is/arenot limited by the accompanying figures. Elements in the figures areillustrated for simplicity and clarity, and have not necessarily beendrawn to scale.

FIG. 1 illustrates an example of an Internet-of-Things (IoT) deploymentaccording to some embodiments.

FIG. 2 illustrates an example of an Information Handling System (IHS)implementation according to some embodiments.

FIG. 3 illustrates an example of an IoT device implementation accordingto some embodiments.

FIG. 4 illustrates examples of IoT services according to someembodiments.

FIG. 5 illustrates an example of a method for overload management of anIoT gateway according to some embodiments.

DETAILED DESCRIPTION

To facilitate explanation of the various systems and methods discussedherein, the following description has been split into sections. Itshould be noted, however, that the various sections, headings, andsubheadings used herein are for organizational purposes only, and arenot meant to limit or otherwise modify the scope of the description orthe claims.

A. Overview

The Internet-of-Things (IoT) is an inter-networking of “things” or“objects” (generally referred to as “IoT devices”) that promotes thecollection and exchange of data among those objects. Generally speaking,IoT technology allows IoT devices to operate remotely across a networkinfrastructure to integrate the physical world into computer-basedsystems using a variety of different communication protocols. In thenear future, it is expected that IoT will be used to automate nearlyevery field of human endeavor.

To name but a few examples, in the field of manufacturing, IoT may beused in process automation (chemicals, food, beverage, pharmaceuticals),discrete automation (auto, machine, electronics), and industrialequipment. In the field of transportation and logistics, IoT may be usedin air, automotive, marine, or rail transport, fleet and freightmanagement, cold chain logistics, traffic systems, public transit andtravel, and usage insurance. In the energy field, IoT may be used inpower generation and distribution, smart grids, oil and gas, andrenewable energy. In communications, IoT may be used to support variousinformation technology (IT) services, network services, data centers,and communication equipment. With respect to natural resources, IoT maybe used in agriculture, metals and minerals mining, water and wastemanagement, forestry, fishing, and livestock, and golf courses. Inhealthcare, IoT may be used in hospitals, home care, health care plans,medical laboratories, biotechnology, and medical appliances andequipment. And in retail and hospitality, IoT may be used in hotels,vending machines, amusement parks, restaurants, sports andentertainment, etc.

In several implementations, IoT systems may provide or support servicesranging among: predictive maintenance, process or quality control, fleetmanagement, supply chain and inventory management, smart infrastructure,building optimization, remote asset management, secure and accesscontrol, point-of-sale support, energy management, compliance, safety,and documentation, among many others.

Yet the quintessential example of IoT remains home automation. Modernhome automation deployments (also known as “smart” or “intelligent”homes) can include control and automation of lighting, heating,ventilation, air conditioning (HVAC) systems, and appliances such aswasher/dryers, robotic vacuums, air purifiers, ovens orrefrigerators/freezers that use wired or wireless networking for remotemonitoring and control.

The expansion of IoT into a plethora of new application areas isexpected to generate incredibly large amounts of data from diverse,heterogeneous devices and locations. Nonetheless, there are currently nocentral standards in this field. Consequently, IoT consumers andproviders continue to face many deployment, architecture, analytics, andsecurity challenges.

To address some of these challenges, the inventors hereof have developeda number of systems and methods that have directly applicable to manyIoT environments, deployments, and implementations. Each of thesesystems and methods may be categorized within one or more of thefollowing areas: Acquisition, Transport, Aggregation, Analysis, andControl.

Acquisition encompasses the hardware—the IoT devices—that capture datafrom interactions with the environment, with other machines, with humansor other living things and make it available for transmission over anetwork. Sensors are the nerve ends of IoT, and a growing assortment ofdevices are collecting data. There are cases where historical data maybe analyzed to provide business practice improvements (not all dataneeds to originate from sensors).

Transport takes the acquired data from various sensors and moves it overa network for aggregation and analysis. As the name implies, the finalstages of data transport generally flow over communication protocols(e.g., TCP/IP and others referred to below), and may be transformed intoInternet friendly data formats like JSON or XML.

Aggregation is responsible for the collection and distribution of outputdata to designated consumers. Consumers can include databases, on-siteservices, analytics services, enterprise service buses, third-partycloud services and similar repositories.

Analysis takes the aggregated data and turns it into operationalinsights by applying context specific algorithms, rules, and predictivemodels. In most deployments, IoT analytics may include feedbackcapabilities so that the predictive models get better over time. In somecases, analytics may be run in the cloud or on the edge such as on anIoT gateway device.

Control provides the ability to act based upon insights gleaned from theanalysis of IoT data. Different types of control actions available mayrange from graphical representation to humans, who can then take manualactions, to fully autonomous systems that can take orchestrated actionsto improve operations, recognize and mitigate failures and threats, andprevent hazards.

For example, consider a relatively simple use case of environmentalmonitoring of an office building. Assume, that there are sensorsinstalled throughout the building to monitor temperature and carbonmonoxide levels; this is part of the aforementioned data aggregationcomponent of IoT. As part of the transport component, there are manytechnology protocols that may be used to transport the collected data,including BACnet (Building and Automation Control networks), Zigbee,Bluetooth Low Energy, Wi-Fi, and others, which may use IoT gateway(s) totranslate the sensors' data or communications to a cloud or remotebackend server.

From the gateway(s), data is communicated through an aggregation layeras part of the aggregation component. The aggregated data reaches acloud based analysis engine that enables the system to responds tochanges in the monitored environment. For instance, such a system may beused to enforce a rule such that, if a room temperature gets too hot, acommand is issued to turn up the A/C.

Overlaying each of these components are techniques related to security,data governance, and systems management of the IoT infrastructure.

To illustrate an example of an IoT environment where the systems andmethods described herein may be implemented, FIG. 1 shows IoT deployment100 according to some embodiments. Particularly, deployment 100 includesIoT device(s) 101, such as building automation and data devices,surveillance devices, HVAC devices, smart metering and sub-metering,lighting devices, etc., which provide and receive data of a networkusing one or more communication protocols 102, such as Ethernet, BACnet(Building Automation and Control), Controller Area Network (CAN bus),Modbus, Zigbee, Bluetooth, Wi-Fi, RFID, etc.

Using protocol(s) 102, IoT devices 101 communicate with IoT gateway(s)103. In several implementations, IoT gateway(s) 103 may include servicessuch as protocol translation 104A, device management 104B, dataaggregation 104C, and edge analytics 104N. In many cases, elements101-103 may be disposed or employed in the same premises (e.g., abuilding, a home, a vehicle, etc.) and/or may be owned by (or licensedto) the same entity or consumer.

In many implementations, however, gateway(s) 103 may also be incommunication with cloud or remote server(s) 105, which can then provideservices such as IT system data integration 106A, big data analytics106B, and visualization and reporting 106N. For example, cloud or remoteserver(s) may be provided or operated by a third-party remotely locatedwith respect to the premises where the IoT device(s) 101 and gateway(s)103 are deployed.

Here it should be emphasized that IoT deployment 100 is depicted forsake of illustration only. There are virtually infinite differentconfigurations possible in any given IoT deployment. In fact, it isoften desirable that a given IoT installation remain flexible, so thatnew and different IoT devices, gateways, switches, access points,servers, services, etc. may be added, removed, or replaced, as the IoTnetwork evolves over time. Although the techniques discussed herein areimmediately applicable to the example IoT deployment 100 of FIG. 1, itis understood that the same techniques may be equally application to anyIoT environment.

B. Hardware

In some embodiments, one or more of gateway(s) 103, server(s) 105,and/or IoT devices 101 shown in FIG. 1 may be implemented as anInformation Handling System (IHS). For purposes of this disclosure, anIHS may include any instrumentality or aggregate of instrumentalitiesoperable to compute, calculate, determine, classify, process, transmit,receive, retrieve, originate, switch, store, display, communicate,manifest, detect, record, reproduce, handle, or utilize any form ofinformation, intelligence, or data for business, scientific, control, orother purposes.

For example, an IHS may be a personal computer (e.g., desktop orlaptop), tablet computer, mobile device (e.g., Personal DigitalAssistant (PDA) or smart phone), server (e.g., blade server or rackserver), a network storage device, or any other suitable device and mayvary in size, shape, performance, functionality, and price. An IHS mayinclude Random Access Memory (RAM), one or more processing resourcessuch as a Central Processing Unit (CPU) or hardware or software controllogic, Read-Only Memory (ROM), and/or other types of NVMs.

Additional components of an IHS may include one or more disk drives, oneor more network ports for communicating with external devices as well asvarious I/O devices, such as a keyboard, a mouse, touchscreen, and/or avideo display. An IHS may also include one or more buses operable totransmit communications between the various hardware components.

FIG. 2 is a block diagram of an example of an IHS. Although IHS 200 maybe used to build any component shown in FIG. 1, it is particularlyapplicable to implementations of IoT gateway(s) 103. In some situations,an IoT gateway can have additional compute added if edge analytics areneeded on the gateway at the network edge, as opposed to beingdistributed in the cloud/backend server.

As shown, IHS 200 includes one or more CPUs 201. In various embodiments,IHS 200 may be a single-processor system including one CPU 201, or amulti-processor system including two or more CPU(s) 201 (e.g., two,four, eight, or any other suitable number). CPU(s) 201 may include anyprocessor capable of executing program instructions. For example, invarious embodiments, CPU(s) 201 may be general-purpose or embeddedprocessors implementing any of a variety of Instruction SetArchitectures (ISAs), such as the x86, POWERPC®, ARM®, SPARC®, or MIPS°ISAs, or any other suitable ISA. In multi-processor systems, each ofCPU(s) 201 may commonly, but not necessarily, implement the same ISA.

In some cases, one or more of CPU(s) 201 may include a GraphicsProcessing Unit (GPU), field programmable gate array (FPGA), or othersuitable integrated component that is specifically used to performanalytics (e.g., machine learning).

CPU(s) 201 are coupled to northbridge controller or chipset 202 viafront-side bus 203. Northbridge controller 202 may be configured tocoordinate I/O traffic between CPU(s) 201 and other components. Forexample, in this particular implementation, northbridge controller 202is coupled to graphics device(s) 204 (e.g., one or more video cards oradaptors) via graphics bus 205 (e.g., an Accelerated Graphics Port orAGP bus, a Peripheral Component Interconnect or PCI bus, or the like).

Northbridge controller 202 is also coupled to system memory 206 viamemory bus 207, and to hard disk drive (HDD) 218. Memory 206 may beconfigured to store program instructions and/or data accessible byCPU(s) 201. In various embodiments, memory 206 may be implemented usingany suitable memory technology, such as static RAM (SRAM), synchronousdynamic RAM (SDRAM), nonvolatile/Flash-type memory, or any other type ofmemory. Conversely, HDD 218 may include any magnetic, solid-state (SSD),or hybrid data storage device capable of storing an OS and otherapplications.

In operation, CPU(s) 201 execute program instructions that are stored inmemory 206 and/or HDD 218. Under control of those instructions, IHS 200may be configured to provide a number or services described in moredetail below.

Northbridge controller 202 is coupled to southbridge controller orchipset 208 via internal bus 209. Generally speaking, southbridgecontroller 208 may be configured to handle various of IHS 200's I/Ooperations, and it may provide interfaces such as, for instance,Universal Serial Bus (USB), audio, serial (e.g., RS232, RS485, CANbus,RS422, etc.), parallel, Ethernet, or the like via port(s), pin(s) (e.g.GPIO or General-Purpose Input Output), and/or adapter(s) 216 over bus217.

For example, southbridge controller 208 may be configured to allow datato be exchanged between IHS 200 and other devices, such as other IHSsattached to a network (e.g., network 101). In various embodiments,southbridge controller 208 may support communication via wired orwireless general data networks, such as any suitable type of Ethernetnetwork, for example; via telecommunications/telephony networks such asanalog voice networks or digital fiber communications networks; viastorage area networks such as Fiber Channel SANs; or via any othersuitable type of network and/or protocol.

Southbridge controller 208 may also enable connection to one or morekeyboards, keypads, touch screens, scanning devices, voice or opticalrecognition devices, or any other devices suitable for entering orretrieving data. Multiple I/O devices may be present in IHS 200. In someembodiments, I/O devices may be separate from IHS 200 and may interactwith IHS 200 through a wired or wireless connection. As shown,southbridge controller 208 is further coupled to one or more PCI devices210 (e.g., modems, network cards, sound cards, or video cards) and toone or more SCSI controllers 214 via parallel bus 211.

Southbridge controller 208 is also coupled to BIOS/UEFI 212 and to SuperI/O Controller 213 via Low Pin Count (LPC) bus 215. BIOS/UEFI 212includes non-volatile memory having program instructions stored thereon.Those instructions may be usable by CPU(s) 201 to initialize and testother hardware components and/or to load an Operating System (OS) ontoIHS 200. Super I/O Controller 213 combines interfaces for a variety oflower bandwidth or low data rate devices. Those devices may include, forexample, floppy disks, parallel ports, keyboard and mouse, temperaturesensor and fan speed monitoring/control, among others. In variousimplementations, southbridge controller 208 may be configured to allowdata to be exchanged between BIOS/UEFI 212 and another IHS attached to anetwork (e.g., a remote server or other source of technical service)using wired or wireless capabilities of network adapter 216.

In some cases, IHS 200 may be configured to provide access to differenttypes of computer-accessible media separate from memory 206. Generallyspeaking, a computer-accessible medium may include any tangible,non-transitory storage media or memory media such as electronic,magnetic, or optical media—e.g., magnetic disk, a hard drive, aCD/DVD-ROM, a Flash memory, etc. coupled to IHS 200 via northbridgecontroller 202 and/or southbridge controller 208.

The terms “physical,” “hardware,” “tangible,” and “non-transitory,” whenused in the context of computer-readable storage or memories, areintended to describe devices excluding propagating electromagneticsignals; but are not intended to otherwise limit the type of physicalstorage device. For instance, the aforementioned terms are intended toencompass types of hardware, physical storage devices that do notnecessarily store information permanently, including, for example, RAM.Program instructions and data stored on a physical memory device innon-transitory form may afterwards be transmitted by transmission mediaor signals such as electrical, electromagnetic, or digital signals, as aseparate or independent process, which may then be conveyed via acommunication medium such as a network and/or a wireless link.

A person of ordinary skill in the art will appreciate that IHS 200 ismerely illustrative and is not intended to limit the scope of thedisclosure described herein. In particular, any computer system and/ordevice may include any combination of hardware or software capable ofperforming certain operations described herein. In addition, theoperations performed by the illustrated components may, in someembodiments, be performed by fewer components or distributed acrossadditional components. Similarly, in other embodiments, the operationsof some of the illustrated components may not be performed and/or otheradditional operations may be available.

For example, in some implementations, northbridge controller 202 may becombined with southbridge controller 208, and/or be at least partiallyincorporated into CPU(s) 201. In other implementations, one or more ofthe devices or components shown in FIG. 2 may be absent, or one or moreother components may be present. For instance, in some cases, IHS 200may include a Trusted Platform Module (TPM) or secure cryptoprocessor,not shown in FIG. 2 for sake of simplicity. But it should be readilyunderstood that the systems and methods described herein may beimplemented or executed with other IHS configurations.

In various embodiments, IHS 200 may be contained within a chassis, case,or other enclosure. And, in many applications, such a chassis may havean industrial or rugged design that can be fan-less, operate within atemperature range (e.g., −10° C.-70° C.), support multiple powersupplies and/or wireless antennas, etc.

Referring now to FIG. 3, any given one of IoT devices 101 of FIG. 1 maybe implemented as device 300. It should be noted, however, that IoTdevice architectures typically vary widely from device to device.Generally speaking, IoT devices range from legacy sensors and actuators(e.g., interfaced via adaptors, hubs, or other circuitry that providesnetwork connectivity) to sophisticated embedded devices and IHSs, suchas IHS 200 of FIG. 2.

Therefore, although device 300 is likely to be found in a modern IoTenvironment, it should also be kept in mind that the various componentsof device 300 are discussed for sake of illustration only. It should bereadily understood, however, that certain systems and methods describedherein may be implemented or executed with other IoT deviceconfigurations.

Referring back to FIG. 3, IoT device 300 includes processing unit 301,signal conditioning unit 302, wireless interface 303, and wiredinterface 304. Processing unit 301 includes processor or controller 305and memory 306. Signal conditioning unit 302 includes digital/analogprocessing circuitry 307, digital-to-analog converter (DAC) 308, andanalog-to-digital converter (ADC) 309.

Wireless interface 303 may include any hardware, circuitry, and/orsoftware that enables IoT device 300 to receive and/or transmit dataover a wireless medium. Examples of wireless networks include, but arenot limited to, Wi-Fi, Bluetooth, BLE, ZigBee, Z-wave, 6LoWPAN, Thread,Sigfox, LoRA, WirelessHD, WiGig, HaLow, NFC, RFID, SigFox LoRaWAN,Ingenu, Weightless, ANT, DigiMesh, MiWi EnOcean, Dash7, or WirelessHARTnetworks, cellular networks (e.g., second generation (2G), thirdgeneration (3G), fourth generation (4G), a Long Term Evolution (LTE), afifth generation (5G) network), and satellite networks. Typically,wireless interface(s) 303 are used to communicate data between IoTdevices, IoT gateways, backend servers, etc. (“to/from IoT network”).

Wired interface 304 may include any hardware, circuitry, and/or softwarethat enables IoT device 300 to receive and/or transmit data over a wiredmedium. Examples of wired networks include Ethernet, cable, opticalfiber, USB, HDMI, DSL, PowerLine, HomePlug, HomePNA, X10, and PublicSwitched Telephone Networks (PSTN). Similarly as above, wiredinterface(s) 304 may also be used to communicate data over an IoTnetwork.

Additionally or alternatively, wired interface 304 may include circuitryconfigured to receive and transmit digital signals or data such as, forexample, RS232, RS485, CANbus, RS422, USB, video signals (e.g., to andfrom a monitor or camera), and GPIO. Additionally or alternatively,wired interface 304 may be used to transmit and receive analog signalsusable to indicate and/or to control the status of buttons, switches,contactors, actuators, etc. (“to/from sensor(s)/actuator(s)”).

Processor or controller 305 and memory 306 operate similarly as CPU(s)201 and memories 206 and 218 of IHS 200. That is, processor 305 executesprogram instructions that are either stored in the processor itself orin memory 306. Under control of those instructions, IoT device 300 maybe configured to provide a number or services described in more detailbelow. In some cases, a programming device may provide such instructionsto processor/controller 305 using a dedicated PLC interface or the like(“to/from programming device(s)”).

Digital/analog processing circuitry 307 may include any digital oranalog circuitry configured condition input or output signals that arereceived or transmitted by IoT device 300, particularly through wiredinterface(s) 304. For example, analog signals may be transmitted usingDAC circuitry 308 and received using ADC circuitry 309. Accordingly,processing circuitry 307 may include any signal processing circuit(DSP), filter, amplifier, mixer, integrator, limiter, oscillator,impedance, rectifier, etc. In some cases, digital/analog processingcircuitry 307 may be integrated into processor/controller 305.

It should be noted that, it many applications, any hardware equipmentused to interconnect any component in an IoT network may itself be anIoT device (e.g., a wireless access point, a network switch, a legacysensor hub or aggregator, etc.). Additionally or alternatively, in manyapplications, otherwise conventional IHS devices, such as, for example,computers, desktops, smart phones, tablets, etc., may also operate asIoT devices.

C. Services

FIG. 4 illustrates examples of IoT services. In various embodiments,services 400 may be provided and/or enabled via execution of programinstructions by CPU(s) 201 of IHS 200 (FIG. 2) implementing any givenone of IoT gateway(s) 103 (FIG. 1). In this particular implementation,services 400 include device services 401, core services 402, supportingservices 403, and export services 404.

Device services 401 enable IoT gateway(s) 103 to transmit and receivedata to and from IoT devices 101 and/or other IoT gateway(s) 103 overwireless and/or wired interfaces 303 and 304, respectively. In thisembodiment, device services 401 include the following modules ormicroservices: gateway service 405 (Peer-to-Peer or P2P), Modbus service406A, BACnet service 406B, ZigBee service 406C, Zwave service 406D, SNMPservice 406E, MQTT service 406F, BLE service 406G, and virtual service406N (for virtual IoT devices). It should be noted, however, that inother embodiments, device services 401 may include other modules ormicroservices configured to enable IoT gateway(s) 103 to performoperations described herein, including, for example, communicating withany device in the IoT network using a suitable communication protocol.

Core services 402 enable IoT gateway(s) 103 to receive and store data inmemory, to issue commands to IoT devices using device services 401, tomanage metadata and provisioning of IoT devices, as well as IoT deviceregistration and configuration. In this embodiment, core services 402include the following modules or microservices: core data service 407;command service 408; device, behavior, and resource management service409; and registry and configuration service 410. It should be noted,however, that in other embodiments, core services 402 may include othermodules or microservices configured to enable IoT gateway(s) 103 toperform operations described herein.

Supporting services 403 enable IoT gateway(s) 103 to log events generatealerts and notification, and to apply rules, as well as scheduling, andscrubbing. In this embodiment, export services 404 include the followingmodules or microservices: distribution 415 and client registrationmodule 416. It should be noted, however, that in other embodiments,supporting services 403 may include other modules or microservicesconfigured to enable IoT gateway(s) 103 to perform operations describedherein.

Export services 404 enable IoT gateway(s) 103 to distribute data toother IoT gateway(s) 103 and/or server 105, as well as to perform clientregistration operations. In this embodiment, export services 404 includethe following modules or microservices: distribution 415 and clientregistration 416. It should be noted, however, that in otherembodiments, export services 404 may include other modules ormicroservices configured to enable IoT gateway(s) 103 to performoperations described herein.

In various embodiments, any given one of microservices 405-416 may beprovided in the form of program instructions executable by CPU(s) 201.In some cases, all of microservices 405-416 are written in the sameprogramming language. In other cases, however, different microservicesmay be written in different languages. Examples of suitable programminglanguages include, but are not limited to: Java, C, Javascript, C++,Python, Node.js, PHP, Lua., Assembler, Go, SWIFT, Rust, Parasail, B#,Ruby, Haskell, erlang, scala, R, etc.

In operation, microservices 405-416 may communicate with each other anysuitable communication protocol. For example, in some cases,inter-service communications may use RESTful interfaces. In otherembodiments, however, communications may be supported by other protocolssuch as ZeroMQ (0MQ), MQTT, AMPQ, SNMP, DDS, or the like.

D. Example Applications

In some embodiments, a variety of IoT techniques may be implemented, atleast in part, by one or more gateway(s) 103 configured with one or moreof services 400. Examples of these applications are discussed in turnbelow.

-   -   i. Gateway Classification

In some embodiments, cluster analysis may be used to classify large,heterogeneous system installations using enterprise server and clientsystem configuration information. A problem with IoT gateways is that,by itself, the gateway lacks a way to differentiate itself by itsinternals. IoT devices connected to an IoT gateway are key ingredientsin that gateway's classification. While a large deployment may use onegateway model for one type of usage model, it is much more common tohave a large installation of the same gateway model with widely varyingusage models.

Accordingly, techniques may be used for gathering aggregateclassification data for important variables, such as IoT devicesconnected to the gateway and how they are used. Looking across multiplegateways, across multiple sites and geographies, an administrator canemploy this classification method in order to understand the topographyof their IoT landscape.

IoT gateways provide data aggregation and analysis across disparate endpoints. These end points vary in their connection type and their typicaldata access patterns. It is valuable to administrators of IoT Gatewaynetworks to classify gateways by way of their end points, connectiontypes, and data access patterns in order to provide more descriptivetopology. In some embodiments, edge analytics and rules microservice 409may be used to implement these techniques.

Classification may begin by gathering data across a large sample set ofthe population of IoT gateways, including their end points connected andsummaries of each end points utilization rates and data access patterns.These factors are then incorporated into a cluster analysis, such as aK-Means (Least Sum of Squares) algorithm or the like, to produce somenumber of clusters.

Cluster models may vary in the number of clusters produced and thesemodels compared and contrasted to identify which are supported by apriori knowledge of the market. With these new insights, products andsolutions may be offered which target the densest regions of the clusteranalysis with optimized solutions that deliver the best performance andreliability within the primary predictor variables such as the type ofend points connected and their data access patterns.

In some cases, analysis of gateway end point connectivity and accesspatterns allow them to be classified into use case clusters.Additionally or alternatively, identification of cluster centers maydescribe a subset of gateways based on end point device connectivity andutilization. Additionally or alternatively, trends in connectivity andutilization across gateways may be analyzed over time as usages split,merge, and evolve.

-   -   ii. Device Profiles

IoT is more fragmented than ever before. Many IoT devices or sensorsthat are manufactured today operate with a number of differentcommunication protocols. As a result, interoperability within a systemthat includes sensors from different manufacturers operating on multipleprotocols is difficult. It is extremely challenging to mine the datainto a common framework for intelligent analysis and decision making.

And it is impossible to automate a system to command and control asensor based on a condition occurring in another system. For example, ifa system detects extreme temperatures of a car engine (e.g., (−30 C to70 C) it has to slow down the RPM of the motor). If the temperaturesensor and engine are operating under different protocols from differentmanufacturers, it is impossible for a system to detect this conditionand execute the remedy if both the devices are not operating within thesame operating framework.

Accordingly, in some embodiments, systems and methods provided hereindescribe an IoT device (e.g., a sensor) in data format. In someembodiments, device, behavior, and resource management service 409 maybe used to implement these techniques. The description of the device mayenable methods of retrieving data from the device and methods to commandand control the device. Such a description may abstract anyimplementation complexity of any device that communicates over anyprotocol.

In some cases, firmware on a gateway may detect a hot-plug event, walkaddress spaces, probe the newly plugged IoT device, and download adevice profile from the cloud.

Some implementations may involve the pre-provisioning of IoT devices onthe gateway by inspecting the device to determine its identity andstate, and then taking steps to configure the device with a known set ofdefault values prior to registering it with a broader system.Pre-provisioning may enable features such as calibration of the sensorso that the gateway can reliably depend upon the type of informationfrom IoT device (e.g., a pre-provisioning process switches a register onthe sensor so that it only sends temperature in Fahrenheit whenqueried).

In other implementations, legacy devices may have a QR code printed onthe sensor that can be used to pull the profile information of thesensor from the cloud as part of pre-provisioning. In yet otherimplementations, firmware may be included in the sensor thatcommunicates with firmware of the gateway about the type and profile ofthe device which exposes the data to the application layer.

In some embodiments, a new sensor may be added to a software frameworkrunning on a gateway without disturbing the existing configuration onthe gateway and without restarting any service. In other embodiments,firmware on the gateway may be configured to understand the descriptivelanguage provided by the operator and to start acting upon the deviceand soon as it is provisioned on the gateway. The firmware may indicatewith a signal (e.g., blinking LED or sending SMS/email) when a newsensor is provisioned on the gateway. In yet other embodiments, firmwareon the gateway when the operator wants to mine the data from sensorsfrom different manufacturers or protocols.

In some cases, data from all sensors collected at the firmware level maybe similar to each other and all of them may be operated at the highestlevel without any knowledge of the protocol or the system they areoperating in.

In sum, systems and methods described herein may abstract the deviceprotocol from user, for example, by using a provisioning service to getconnection information from sensor directly, describing a device to theframework which is running on the gateway, providing a common commandand control different devices operating on different protocols, and/orcreating a homogenous representation of sensors operating on multipleprotocols from different manufacturers.

iii. Device Identity

Protecting deployed infrastructure in an IoT environment can bedifficult, particularly when dealing with legacy devices and sensors.Due to their age, legacy devices provide little if any protectionagainst tamper, spoofing, data injection, or other malicious behaviorthat an attacker may undertake. Newer devices may provide someprovisions for security but these are often neither comprehensive norfoolproof without careful orchestration and deployment. Without propersafeguards, there is the potential for compromise of sensitiveinformation, destruction of property, and other material loss.

In some cases, systems and methods described herein may augment orenhance the identity of a device by measuring various hardware andsoftware based interactions with it and tracking them over time toestablish a pattern of device characteristics and behavior. Once thebehavioral pattern is established, then deviations from that pattern maybe detected and preventive and corrective actions taken to protectagainst malicious behavior. In some embodiments, device, behavior, andresource management service 409 may be used to implement thesetechniques.

Additionally or alternatively, anomalous behaviors may be detectedacross a group of homogenous sensors—e.g., one behaving unusuallyrelative to others. Additionally or alternatively, anomalous behaviormay be detected across a set of heterogeneous devices—e.g., device isthought to be offline but is registering unusual current/voltage on anassociated power meter. Given that these measurements and theirassessment may only be known to the system, this makes it difficult foran attacker to know what is being measured. Moreover, a system maychange these factors at any time, increasing tampering difficulty.

In various embodiments, measured items may include, but are not limitedto: latency of request/responses, frequency of indications, consistencyof content in responses as compared to expected content, correlationsamong measurements related to the device, from the device itself andother devices, electrical voltage, electrical current, and/or electricalimpedance on physical connections during communications, bit errorrates, SNR, etc., changes in boot times, initial connection times, noiseon a connection during idle periods, and environmental factors, such asdistance relative to signal strength.

As such, systems and methods described herein may collect hardwareand/or software metrics associated with a device, characterize, augmentand establish device identity using collected metrics, perform analysisof collected metrics against established device identity metrics, detectanomalous metrics, take actions based upon detection, and/or allow forreestablishment of identity due to changes in environment, devicecomposition, or other factors.

-   -   iv. Overload Prevention

In some embodiments, systems and methods described herein may performoverload prevention. An overload prevention routine within device,behavior, and resource management service 409 may be used to managegateway resources by making decisions based on multiple data sources. Aresource usage anomaly may cause the overload prevention module to takesteps to prevent anomalous or excessive traffic from entering the systemand configure the gateway to work around the affected services orinterfaces. The device, behavior, and resource management service 409may also be used as a system management capability as a failsafe way tosilence a rogue gateway or managed device.

In some implementations, device, behavior, and resource managementservice 409 may detect anomalous levels of resource consumption by aservice or on an interface compared to an ongoing baseline. To preservefunctionality, the device, behavior, and resource management service 409may reconfigure the affected service or communication medium based oncurrent and historical data. This action may include postponing lowpriority actions, reducing collection rate, volume, devices served,stopping services, and disabling interfaces. The overload preventionroutine may use a blend of operator priority specifications and datacharacteristics to intelligently preserve as much system functionalityas possible, including rerouting communication through other interfaces.

In sum, systems and methods described herein may, using resourceconsumption, device configuration, dynamic data volatility metrics, andservice configuration, balance microservices and communicationsinterfaces to protect against attacks and erroneous states byintelligently degrading capability. These system and methods may alsouse content and context-aware methods to determine which progressivelymore aggressive mitigations options to take.

-   -   v. Safeguard and Recovery

IoT Gateways aggregate data collected by managed IoT devices. In somecases, such data may contain information about power anomalies likely toaffect managed devices immediately or in the near future. Accordingly,in some systems and methods described herein, the gateway may takeaction to preserve system health. In some embodiments, device, behavior,and resource management service 409 may be used to implement thesetechniques.

For example, the gateway may sense an incoming power/environmentalanomaly (e.g., weather, voltage, current, or phase), and it may takeaction to preserve the system. Gateway actions may include, but are notlimited to: graceful shutdown of managed devices, reduction incollection and reporting rate and fields, reduction in running services,reduction in system hardware usage (e.g., drop CPU frequency, etc.),drive parking, handing sensors off to unaffected gateways or routes(e.g., when gateway knows that it or other infrastructure will go down),priority-based device shutdown in limited resource pool, sendingindication to home, notifying to throttle external communicationattempts, etc.

The gateway may also prime itself and devices for post-power restore.Actions may include, but are not limited to: seeding startup timers toprevent all devices from requesting connection at the same time and/orrediscovery behaviors include prioritization of restart and reconnectionof devices.

In some embodiments, device configuration, dynamic data volatilitymetrics, and service configuration may react to power anomalies byintelligently degrading capability. Content and context-aware techniquesmay be used to determine which progressively more aggressive mitigationsoptions to take. Moreover, the same metrics may be used to cause theprocess to restart in order to prioritize the most critical devices anddata.

-   -   vi. Load Balancing

Today enterprise servers use task scheduling, reprioritization, and loadbalancing to maintain an optimal internal state despite wildly varyingenvironmental and traffic conditions. This can be done by evaluating theincoming requests, comparing with current utilization and saturationrates, and determining whether priorities can still be maintained (suchas serving dynamic web content) while resources are heavily utilized forother tasks (such as database requests). A server may opt to rescheduleor reprioritize tasks, or completely reassign request(s) to another nodeon the network in order to maintain its own set of priorities.

IoT gateways are challenged in implementing similar methods to maintainan optimal internal state because, among other things, they aggregatedata across a broad and heterogeneous set of IoT devices (e.g., edgedevices, such as an airflow sensor, video camera, or a door lock). Also,IoT gateways serve a wide variety of purposes, and often their purposeis determined by the devices to which they connect. Moreover, IoTgateways are constrained in performance by a number of internal factorssuch as power, thermals, and available bandwidth to end points.

In various embodiments, techniques are presented for optimizing IoTgateway performance based on utilization and saturation rates, as wellas other factors, of not only the internal components of the gateway(such as the CPU) but also of external devices connected to disparatebus architectures. In many cases, these techniques may provide abilityto automatically adjust the workloads of every IoT gateway in theinstallation to maintain optimal internal states. In some embodiments,device, behavior, and resource management service 409 may be used toimplement these techniques.

IoT gateways are constrained in performance by a number of internalfactors such as power, thermals, and available bandwidth to end points.By analyzing end point access patterns and establishing correlationbetween predictor variables (e.g., log reads and writes, alerts, errors,and similar) and responses (e.g., CPU temperature and powerconsumption), performance can be optimized and long-term reliabilityimproved through task rescheduling, reprioritization, and/or loadrebalancing to other gateways on the network.

In some embodiments, techniques described herein may gather several orall possible predictor variables (e.g., internal instrumentation datawithin the gateway, connected devices, telemetry data for end points,end point traffic classes, etc.), identify desired and avoidableconditions (e.g., running average power targets, running averagetemperature, etc.), identify subset of predictors that explainvariations in the target conditions (e.g., via artificial neuralnetwork), construct a model that describes the relationship betweenpredictor and response, and/or monitor predictors and alter gatewayworkloads steering toward desirable states and away from undesirablestates.

As such, techniques described herein may enable identification ofsuitable times to analyze instrumentation logs to identify opportunitiesto optimize performance and/or reliability, analyze gateway end pointaccess patterns to determine subset of predictor variables correlatingto a targeted (e.g., desirable or avoidable) response, and/or performtask rescheduling, reprioritization, and/or load rebalancing to othergateways on the network.

-   -   vii. Smart Lock

IoT gateways are often deployed in “headless” configurations anddepending on its use case often in remote deployments that arepotentially in various locations inside, outside of buildings, etc. Insome cases, IoT gateway manufacturers may provide a rugged enclosurechassis for installing gateways in harsher or environments needing moresecurity and protection. Moreover, support may be built-in for intrusiondetection which can be reported/alerted to the gateway's managementsystem.

An IoT gateway's chassis, as described herein, may provide not justphysical gateway security and intrusion detection/reporting, but it mayalso prevent an unauthorized person from tampering, updating and using,or potentially hijacking the gateway for other purposes. For example, ifan unauthorized user has physical access to the machine, then there isno security. Once the rugged enclosure is breached, anyone with physicalaccess to the device can press the power button, plug devices into USB,serial, and HDMI/video ports, and thereby use, change, configure, orhighjack the box. In some embodiments, device, behavior, and resourcemanagement service 409 may be used to implement these techniques.

In some embodiments, systems and methods described herein may provide anadditional smart locking capabilities to the gateway; a cyber factor inaddition to conventional intrusion detection. The gateway knows when itis locked physically using the rugged enclosure intrusion detectionswitch connected to the gateway. Using an OS level application, handler,or service (or in another embodiment a security microservice), thegateway may invoke a cyber lock when the intrusion system isclosed/locked.

A cyber lock may additionally or alternatively disable external powerbutton functionality, disable HDMI/video out ports, disable ability toadd new USB, serial, I/O connections, and/or lock down gatewaypolicy/configuration setup including networking setup.

Device, behavior, and resource management service 409 may be used tomonitor hardware intrusion detection (e.g., other embodiments includeBIOS/UEFI modules, OS app/service, etc.). Upon enabling intrusiondetection, the microservice may lock down a configured list—power buttoncontrol, disabling HDMI/video out, disabling ability to add new USB,serial, or I/O connections, protects any further device configuration ordevice setup. Then, upon the intrusion detection switch being triggered,the microservice may report out an invalid intrusion alert to systemmanagement.

The device, behavior, and resource management service 409 may alsoprovide secure remote unlocking by a technician to disable the intrusiondetection for maintenance. This can additionally be provided by localsensing, such as using Bluetooth presence detection of a known key.

Accordingly, systems and methods described herein may provide thecapability to further cyber lock down a device in addition to existingphysical intrusion detection, thus helping prevent further access ordamage to the gateway. These systems and methods may also facilitate thedisablement of hardware power button and unused USB, serial, other I/O,and HDMI/video out ports upon intrusion detection.

E. Overload Management of IoT Gateways

Systems and methods described herein may perform overload management.Particularly, device, behavior, and resource management service 409 maybe used to manage IoT gateway resources. A usage anomaly, when detected,may cause microservice 409 to perform one or more operations configuredto manage anomalous or excessive traffic to or from an IoT gateway,and/or to work around affected services or interfaces.

In some embodiments, IoT gateway “resources” may include one or more of:CPU occupancy, core temperature, memory, disk I/O rate, disk space,interface throughput, interface connectivity limit (number ofsimultaneous clients), and/or stored energy.

Also, in some embodiments, the term “data volatility” (or simply“volatility”) may include historic trends of a “data field” (e.g., atemperature value, speed value, communication or power status, etc.)communicated between an IoT device and the IoT gateway within a “packet”having a number of other “data fields.” These historic trends mayinclude, for example, a maximum, minimum, mean, mode, standard deviationand/or any combination thereof with respect to the corresponding datafield's value(s), as established based upon historic values to create a“baseline.”

In some cases, volatility information may be provided in the form of adatabase, table, or any other suitable format. As such, each data fieldmay be tracked as communications occur, as well as the data field'scorresponding value, over time, to establish the baseline.

In some embodiments, “current volatility” may refer to metrics basedupon current data trends—that is, data being collected at the presenttime—which may be compared with the data field's nominal state. Asdescribed in more detail below, a data field's current volatility mayalso be compared with the baseline in order to select a correspondingresponsive action. For example, a tightly and historically invarianttemperature reading that is currently within its nominal range, in theabsence of external factors, is less critical than a historicallyvariant temperature reading currently near a maxima.

Referring to FIG. 5, an example of method 500 for overload management inan IoT gateway is shown. In some embodiments, method 500 may beexecuted, at least in part, by device, behavior, and resource managementservice 409 provided within an IoT gateway. Generally speaking, method500 may include three distinct phases: initialization 501, normaloperation 502, and overload detection 503.

With respect to initialization 501, at block 504, a user oradministrator may assign different priorities to each IoT device incommunication with the IoT gateway. Additionally or alternatively,different priorities may be assigned to each communication channel orinterface of each IoT device. In some cases, priorities may be binaryvalues (e.g., critical or non-critical), or may assume any other value(e.g., 1 to 5, with the lowest value indicating higher priority).Additionally or alternatively, priorities may be a combination ofvarious data (e.g., a weighted average), including one or more of: datafield priority, device priority, service priority, dependencies (betweenrules and/or between data fields), data volatility, re-routingcapabilities of IoT devices, or re-provisionability of IoT devices.

At block 505, method 500 may include establishing data dependencies,whereby dependencies between data fields, interfaces, and or devices maybe identified. In some cases, dependencies may be used to propagate ormodify priority values across distinct IoT devices, channels, and/orinterfaces whose operation(s) depend upon each other.

At block 506, method 500 may include receiving one or more “volatilitymodels” from a remote server or from the cloud. Each volatility modelmay be used as a template for creating historic data volatilitybaselines, and/or for evaluating how to manage overload conditions inresponse to a comparison between current data volatility metrics and abaseline, as well as the relative priorities of IoT devices orcommunication channels. In some cases, a volatility model may include,for each type or class of IoT device (e.g., motor, HVAC, microphone,etc.), a list of data fields to be obtained from each packetcommunicated to the IoT gateway, a sampling rate for those packets(e.g., inspect every n^(th) packet), etc.

During normal operation 502, method 500 includes receiving resourcedata. At block 508, method 500 compares the resource states to aselected volatility model associated with the IoT device and/orcommunication channel at issue. Then, at block 509, method 500 adds thereceived resource state data to its associated volatility model tocreate a volatility baseline of historical values for that IoT deviceand/or communication channel. Finally, control returns from block 509 toblock 507, therefore creating a loop that enables the IoT gateway tocollect and store resource data continuously or periodically.

In the overload detection phase 503, method 500 detects an overloadcondition in the IoT gateway. For example, an overload condition may bedetected based upon core temperatures (above a threshold), latency orerror rate, resource outages or anomalies, and so on. These conditionsmay be evaluated against one or more threshold values. Moreover, anoverload condition may also be detected based upon a comparison betweenanomalous resource usage against baseline volatility data.

To this end, block 510 detects the overload condition, block 511 readscurrent data values, block 512 determines the current, present-timevolatility, block 513 scores the relative volatility; that is, thedifference between the current volatility and a corresponding volatilitybaseline based on historical data accumulated during normal operation502 and used to populate the selected volatility model.

Then, block 514 determines an action to execute based upon the relativevolatility of block 513, and executes that action at block 515, beforecontrol returns to block 507 in an attempt to maintain the IoT gatewaywithin normal operation 502. Examples of responsive actions include atleast one of: postponing selected operations (e.g., put or get requests,etc.), reducing the size of data fields to reduce the amount of datareceived by the IoT gateway, reducing a packet collection rate forpackets received from one or more IoT devices (e.g., by instructing theIoT device to reduce a data acquisition rate of a sensor), re-routingand/or passing off IoT devices to other IoT gateways or interfaces,disabling IoT gateway supporting services, disabling IoT devices,disabling IoT device services, and/or disabling communication interfacesand re-routing traffic.

The examples described below illustrate various implementations ofmethod 500. Numerous such examples and combinations will be apparent toa person of ordinary skill in the art in light of the various teachingsdescribed herein:

Example A provides an illustration of an application of method 500 toresolve an overload condition with reduced collection volume. Assume,for example, that an IoT gateway provides a given IoT device or sensoraccess to the IoT network. Also assume, for sake of this hypothetical,that the IoT device is configured to operate as “event-driven,” not“schedule-driven” (e.g., a temperature sensor that reports ontemperature change).

If a large temperature variation occurs, the IoT device may produce alarge volume of data in a short time period. As a result, the IoTgateway's CPU load factor increases substantially, reaching an overloadcondition. Using method 500, however, device, behavior, and resourcemanagement service 409 detects the condition and reduces the collectedvolume rate for that IoT device.

In some cases, service 409 may process fewer packets originated from theIoT device. Additionally or alternatively, service 409 may de-prioritizeor ignore high volatility data fields, therefore prioritizinglow-priority and non-volatile data fields for each packet from that IoTdevice. Additionally or alternatively, service 409 may instruct the IoTdevice to reduce the sampling rate of the IoT device's own datacollection processes (e.g., to provide fewer temperature readouts perunit of time), insofar as the data collection process uses data field(s)determined to depart from the baseline volatility data.

Example B provides an illustration of an application of method 500 toresolve an overload condition with device migration. Assume thatexternal conditions cause less efficient CPU cooling within a first IoTgateway. As a result, the CPU temperature increases substantially,reaching an overload condition. As such, the IoT gateway detects thiscondition and migrates a movable IoT device to a second, unloaded IoTgateway, provided the second gateway has the necessary interface formanaging the movable device.

Example C provides an illustration of an application of method 500 toresolve an overload condition with intelligent capability degradation.Assume that a resource overload condition is met, but the IoT gatewaydetermines that no reduction of collection or pass-off of IoT devices ispossible. In that case, the IoT gateway may calculate priority levels ofeach device service, for example, based on the highest priority level ofanother service dependent on it (e.g., actuation of an HVAC fan servicemay depend upon a temperature reading service and, if the temperaturereading service has the highest priority level among other services, theHVAC fan service may inherit the priority of the temperature readingservice), thereby selectively degrading otherwise its availableservices. Then, the IoT gateway shuts down the lowest priorityservice(s), as needed.

In each of examples A-C, the process may be repeated until the resourceoverload condition is no longer detected. Moreover, in variousembodiments, examples A-C may be combined in any suitable manner, suchthat overload conditions may be addressed using reduced collectionvolume, device migration, and/or capability degradation, whether incombination or independently of each other.

* * *

It should be understood that various operations described herein may beimplemented in software executed by logic or processing circuitry,hardware, or a combination thereof. The order in which each operation ofa given method is performed may be changed, and various operations maybe added, reordered, combined, omitted, modified, etc. It is intendedthat the invention(s) described herein embrace all such modificationsand changes and, accordingly, the above description should be regardedin an illustrative rather than a restrictive sense.

Although the invention(s) is/are described herein with reference tospecific embodiments, various modifications and changes can be madewithout departing from the scope of the present invention(s), as setforth in the claims below. Accordingly, the specification and figuresare to be regarded in an illustrative rather than a restrictive sense,and all such modifications are intended to be included within the scopeof the present invention(s). Any benefits, advantages, or solutions toproblems that are described herein with regard to specific embodimentsare not intended to be construed as a critical, required, or essentialfeature or element of any or all the claims.

Unless stated otherwise, terms such as “first” and “second” are used toarbitrarily distinguish between the elements such terms describe. Thus,these terms are not necessarily intended to indicate temporal or otherprioritization of such elements. The terms “coupled” or “operablycoupled” are defined as connected, although not necessarily directly,and not necessarily mechanically. The terms “a” and “an” are defined asone or more unless stated otherwise. The terms “comprise” (and any formof comprise, such as “comprises” and “comprising”), “have” (and any formof have, such as “has” and “having”), “include” (and any form ofinclude, such as “includes” and “including”) and “contain” (and any formof contain, such as “contains” and “containing”) are open-ended linkingverbs. As a result, a system, device, or apparatus that “comprises,”“has,” “includes” or “contains” one or more elements possesses those oneor more elements but is not limited to possessing only those one or moreelements. Similarly, a method or process that “comprises,” “has,”“includes” or “contains” one or more operations possesses those one ormore operations but is not limited to possessing only those one or moreoperations.

1. An Information Handling System (IHS), comprising: one or moreprocessors; and a memory coupled to the one or more processors, thememory including program instructions stored thereon that, uponexecution by the one or more processors, cause the IHS to: detect anoverload condition in the IHS; in response to the detection, compare acurrent volatility of a data field against a volatility baseline forthat data field, wherein the data field is one of a plurality of otherfields contained within a packet communicated between anInternet-of-Things (IoT) device and the IHS; and take responsive actionbased, at least in part, upon the comparison.
 2. The IHS of claim 1,wherein the overload condition includes at least one of: a coretemperature above a threshold, latency or error rate above anotherthreshold, or a service outage.
 3. The IHS of claim 1, wherein thevolatility baseline is created based upon historical metrics associatedwith the data field.
 4. The IHS of claim 3, wherein the volatilitybaseline is built by populating a volatility model with data obtainedfrom inspecting previous packets communicated between the IoT device andthe IHS.
 5. The IHS of claim 4, wherein the volatility model includes alist of data fields to be obtained from each packet communicated to theIHS.
 6. The IHS of claim 1, wherein the responsive action includes atleast one of: postponing an operation, reducing the size of the datafield, re-routing the communication to a different interface, passingthe IoT device to another IHS, or disabling the IoT device.
 7. The IHSof claim 1, wherein the responsive action includes reducing a packetcollection rate for subsequent packets communicated between the IoTdevice and the IHS.
 8. The IHS of claim 1, wherein the responsive actionincludes instructing the IoT device to reduce a data acquisition rate ofa sensor within the IoT device.
 9. A hardware memory device havingprogram instructions stored thereon that, upon execution by anInformation Handling System (IHS), cause the IHS to: detect an overloadcondition in the IHS; in response to the detection, compare a currentvolatility of a data field against a volatility baseline for that datafield, wherein the data field is one of a plurality of other fieldscontained within a packet communicated between an Internet-of-Things(IoT) device and the IHS; and take responsive action based, at least inpart, upon the comparison.
 10. The hardware memory device of claim 9,wherein the overload condition includes at least one of: a coretemperature above a threshold, latency or error rate above anotherthreshold, or a service outage.
 11. The hardware memory device of claim9, wherein the volatility baseline is created based upon historicalmetrics associated with the data field.
 12. The hardware memory deviceof claim 11, wherein the volatility baseline is built by populating avolatility model with data obtained from inspecting previous packetscommunicated between the IoT device and the IHS.
 13. The hardware memorydevice of claim 12, wherein the volatility model includes a list of datafields to be obtained from each packet communicated to the IHS.
 14. Thehardware memory device of claim 9, wherein the responsive actionincludes at least one of: postponing an operation, reducing the size ofthe data field, re-routing the communication to a different interface,passing the IoT device to another IHS, or disabling the IoT device. 15.The hardware memory device of claim 9, wherein the responsive actionincludes reducing a packet collection rate for subsequent packetscommunicated between the IoT device and the IHS or instructing the IoTdevice to reduce a data acquisition rate of a sensor within the IoTdevice.
 16. A method, comprising: detecting an overload condition in theIHS; in response to the detection, comparing a current volatility of adata field against a volatility baseline for that data field, whereinthe data field is one of a plurality of other fields contained within apacket communicated between an Internet-of-Things (IoT) device and theIHS; and taking responsive action based, at least in part, upon thecomparison.
 17. The method of claim 16, wherein the overload conditionincludes at least one of: a core temperature above a threshold, latencyor error rate above another threshold, or a service outage.
 18. Themethod of claim 16, further comprising building the volatility baselineby populating a volatility model with data obtained from inspectingprevious packets communicated between the IoT device and the IHS. 19.The method of claim 16, wherein the volatility model includes a list ofdata fields to be obtained from each packet communicated to the IHS. 20.The method of claim 16, wherein the responsive action includes reducinga packet collection rate for subsequent packets communicated between theIoT device and the IHS and instructing the IoT device to reduce a dataacquisition rate of a sensor within the IoT device.